Skip to content

Merge node-info 0.28.0 (main) into deploy - #42

Merged
dmmdea merged 6 commits into
deployfrom
deploy-merge-node-info-0.28.0
Nov 8, 2026
Merged

dmmdea merged 6 commits into
deployfrom
deploy-merge-node-info-0.28.0

Conversation

@dmmdea

@dmmdea dmmdea commented Nov 8, 2026

Copy link
Copy Markdown
Owner

Brings fork PR #41 (node-info 0.28.0) from main into deploy.

  • Clean merge, no conflicts. services/versions.json keeps nvpair-workload-manager: 0.16.0+fork and takes nvpair-node-info: 0.28.0.
  • services/nvpair-node-info here is byte-identical to 8e0281f, the commit the 0.28.0 deploy binaries were built from, so the staged builds match this branch.
  • Nothing else changes on deploy: the engine-widen and workload-manager ingress patches are untouched.

🤖 Generated with Claude Code

dmmdea and others added 6 commits October 13, 2026 22:12
Merge upstream v1.0.0 into main
Detect PCI vendor 0x1f4b cards and list each as a kind "npu" accelerator row,
not inference-ready and outside GPU telemetry, like the Coral and RKNPU rows.
A single axcl-smi table call every 5 s (5 s timeout, never overlapping) feeds
the card name, CMM pool capacity and usage, NPU utilization and temperature;
the last good table is published for at most 20 s. A "--" NPU reading is
reported as utilization_unavailable, never as 0. Without the CLI the card is
still listed from PCI. Power is not reported by the card and is omitted.

gpuStat gains VRAMTotal so a sampler can supply a capacity the static
inventory does not know.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Signed-off-by: dmmdea <4965968+dmmdea@users.noreply.github.com>
…arams

Two Windows node-info defects seen on a three-card host:

- No GPU temperature at all. NVIDIA-SMI 621.14 prints temperature.gpu
  with decimals ("78.76"); the integer-only parse rejected every row, so
  every card lost its temperature while power and utilization (parsed as
  floats/ints) stayed. parseCelsius (beside parseWatts) accepts whole and
  fractional degrees and rounds; the Linux collector uses it too.

- Intermittent "IDXGIFactory1::EnumAdapters1 failed; stopping enumeration
  idx=0 hr=0x00000000" (hundreds per day). vtableCall receives
  out-parameters as uintptr(unsafe.Pointer(&local)); without
  //go:uintptrescapes the local stays on the goroutine stack, and a stack
  move inside the call makes DXGI write to the old address, so the caller
  sees S_OK with a nil adapter and the pass reports no adapters (the
  temperature join and inventory refresh then work from an empty list).
  go build -gcflags=-m: before "adapter does not escape", after "moved to
  heap: adapter". Same directive as syscall.(*LazyProc).Call.

Signed-off-by: dmmdea <4965968+dmmdea@users.noreply.github.com>
…re fix

Signed-off-by: dmmdea <4965968+dmmdea@users.noreply.github.com>
node-info 0.28.0: Axera AX650N rows, R620+ GPU temperature, stable DXGI out-params
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dmmdea
dmmdea merged commit 56286e7 into deploy Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant